Conversation
[Release] v1.387.0
[Release] v1.388.0
[Release] v1.389.0
[Release] v1.390.0
Corrected typos in instructions for accessing Vaultwarden and NGINX configuration.
Updated notes and warnings to improve clarity and accuracy regarding Docker installation and configuration on Ubuntu 24.04.
There is no provision for "warnings" or "important" in this, just use "note" everywhere you need to call something out.
✅ Deploy Preview for nostalgic-ptolemy-b01ab8 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Hi @DHBR2 and @nmelehan-akamai may be i am missing something. I was not successful in testing this guide. I have attached the output of the termial text so that you can see the steps that did not work for me.
Terminal Saved Output- vaultwarden.txt
Hi @DHBR2 and @nmelehan-akamai I am sorry that the terminal output that I shared earlier included all the output since i configured my new laptop including the git confgurations.
Here's the output that you might wamt to test for the vaultwarden.
valtwarden..pdf
...guides/security/authentication/self-host-vaultwarden-passwd-manager-on-ubuntu-22-04/index.md
Show resolved
Hide resolved
...guides/security/authentication/self-host-vaultwarden-passwd-manager-on-ubuntu-22-04/index.md
Show resolved
Hide resolved
| ```command | ||
| hostnamectl | ||
| timedatectl | ||
| ``` | ||
| Expected output similar to: | ||
| ```output | ||
| Static hostname: vaultserver | ||
| Operating System: Ubuntu 24.04 LTS | ||
| Architecture: x86-64 | ||
|
|
||
| Local time: Wed 2025-11-05 09:45:00 PST | ||
| System clock synchronized: yes | ||
| NTP service: active | ||
| Time zone: America/Los_Angeles (PST, -0800) | ||
| ``` |
There was a problem hiding this comment.
The output on ubuntu 24.04 is slightly different.
rajie@vaultwarden-test:/srv/vaultwarden$ hostnamectl
Static hostname: vaultwarden-test
Icon name: computer-vm
Chassis: vm 🖴
Machine ID: d0e2ac542d4d4da48956903881db595e
Boot ID: 45bd4a101bca488d926dff70705507d3
Virtualization: kvm
Operating System: Ubuntu 24.04.4 LTS
Kernel: Linux 6.8.0-71-generic
Architecture: x86-64
Hardware Vendor: Linode
Hardware Model: Compute Instance
Firmware Version: Not Specified
rajie@vaultwarden-test:/srv/vaultwarden$ timedatectl
Local time: Tue 2026-03-03 20:28:36 IST
Universal time: Tue 2026-03-03 14:58:36 UTC
RTC time: Tue 2026-03-03 14:58:36
Time zone: Asia/Kolkata (IST, +0530)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
rajie@vaultwarden-test:/srv/vaultwarden$
There was a problem hiding this comment.
The guide has been corrected to show Ubuntu 22.04.
...guides/security/authentication/self-host-vaultwarden-passwd-manager-on-ubuntu-22-04/index.md
Show resolved
Hide resolved
...guides/security/authentication/self-host-vaultwarden-passwd-manager-on-ubuntu-22-04/index.md
Outdated
Show resolved
Hide resolved
| Step 4: Then restart Vaultwarden: | ||
| ```command | ||
| docker compose down | ||
| docker compose up -d |
There was a problem hiding this comment.
There is no compose file so this step did not work:
rajie@vaultwarden-test:/srv/vaultwarden$ cd ..
rajie@vaultwarden-test:/srv$ cd ..
rajie@vaultwarden-test:/$ cd /home/rajie/vaultwarden
bash: cd: /home/rajie/vaultwarden: No such file or directory
rajie@vaultwarden-test:/$ cd /srv/vaultwarden/
rajie@vaultwarden-test:/srv/vaultwarden$ sudo nano .env
[sudo] password for rajie:
rajie@vaultwarden-test:/srv/vaultwarden$ docker compose down
no configuration file provided: not found
rajie@vaultwarden-test:/srv/vaultwarden$ docker compose up -d
no configuration file provided: not found
rajie@vaultwarden-test:/srv/vaultwarden$
There was a problem hiding this comment.
The Vaultwarden Deployment section has been moved to fit the natural flow of how you set things up. Thank you for you review and I hope it works better for you now.
|
Hi @DHBR2 I just tested and validated the guide on Ubuntu 24.04 as mentioned in #7358. There were very few minor discrepancies I noticed and I have provided them as suggestions. |
Rajakavitha1
left a comment
There was a problem hiding this comment.
The guide works as documnted just a few minoe suggestions based on the validation on Ubuntu 24.04
| @@ -0,0 +1,633 @@ | |||
| --- | |||
| slug: self-host-vaultwarden-passwd-manager-on-ubuntu-22-04 | |||
There was a problem hiding this comment.
| slug: self-host-vaultwarden-passwd-manager-on-ubuntu-22-04 | |
| slug: self-host-vaultwarden-passwd-manager-on-ubuntu-24-04 |
| @@ -0,0 +1,633 @@ | |||
| --- | |||
| slug: self-host-vaultwarden-passwd-manager-on-ubuntu-22-04 | |||
| title: "Self-Hosting Vaultwarden Password Manager on Ubuntu 22.04" | |||
There was a problem hiding this comment.
| title: "Self-Hosting Vaultwarden Password Manager on Ubuntu 22.04" | |
| title: "Self-Hosting Vaultwarden Password Manager on Ubuntu 24.04" |
| authors: ["Diana Hoober"] | ||
| contributors: ["Diana Hoober"] | ||
| published: 2025-10-10 | ||
| keywords: ['vaultwarden','bitwarden','password manager', 'install vaultwarden', 'open source password management', 'self-hosted', 'lightweight', 'Ubuntu 22.04', 'bitwarden replacement', 'bitwarden compatible'] |
There was a problem hiding this comment.
| keywords: ['vaultwarden','bitwarden','password manager', 'install vaultwarden', 'open source password management', 'self-hosted', 'lightweight', 'Ubuntu 22.04', 'bitwarden replacement', 'bitwarden compatible'] | |
| keywords: ['vaultwarden','bitwarden','password manager', 'install vaultwarden', 'open source password management', 'self-hosted', 'lightweight', 'Ubuntu 24.04', 'bitwarden replacement', 'bitwarden compatible'] |
| license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' | ||
| --- | ||
|
|
||
| This guide walks you through deploying Vaultwarden—a lightweight, Bitwarden-compatible password manager—using Docker and NGINX on Ubuntu 22.04 LTS. It’s designed for clarity, validation, and long-term maintainability, with a focus on predictable behavior and user trust. |
There was a problem hiding this comment.
| This guide walks you through deploying Vaultwarden—a lightweight, Bitwarden-compatible password manager—using Docker and NGINX on Ubuntu 22.04 LTS. It’s designed for clarity, validation, and long-term maintainability, with a focus on predictable behavior and user trust. | |
| This guide walks you through deploying Vaultwarden—a lightweight, Bitwarden-compatible password manager—using Docker and NGINX on Ubuntu 24.04 LTS. It’s designed for clarity, validation, and long-term maintainability, with a focus on predictable behavior and user trust. |
|
|
||
| Before starting, ensure your server is secure and ready: | ||
|
|
||
| - Ubuntu 22.04 LTS installed and configured |
There was a problem hiding this comment.
| - Ubuntu 22.04 LTS installed and configured | |
| - Ubuntu 24.04 LTS installed and configured |
|
|
||
| 3. Stop the running container: | ||
| ```command | ||
| docker compose down |
There was a problem hiding this comment.
| docker compose down | |
| sudo docker compose down |
|
|
||
| 4. Recreate and start the updated container: | ||
| ```command | ||
| docker compose up -d |
There was a problem hiding this comment.
| docker compose up -d | |
| sudo docker compose up -d |
| container_name: vaultwarden | ||
| restart: unless-stopped | ||
| ports: | ||
| - "127.0.0.1:3012:80" |
There was a problem hiding this comment.
| - "127.0.0.1:3012:80" | |
| - "<your-server-ip>:3012:80" |
|
|
||
| Final Validation Checklist | ||
|
|
||
| - [ ] Vaultwarden is running and bound to 127.0.0.1:3012 |
There was a problem hiding this comment.
| - [ ] Vaultwarden is running and bound to 127.0.0.1:3012 | |
| - [ ] Vaultwarden is running and bound to <your-server-ip>:3012 |
| ADMIN_TOKEN: your_generated_token_here | ||
| ``` | ||
|
|
||
| Replace `your_generated_token_here` with the secure admin token you created. |
There was a problem hiding this comment.
| Replace `your_generated_token_here` with the secure admin token you created. | |
| Replace `your_generated_token_here` with the secure admin token you created in step 1 |
| ```command | ||
| # Vaultwarden reverse proxy configuration | ||
| # Replace 'your-domain-name' with your actual domain | ||
| # Ensure Vaultwarden is bound to 127.0.0.1:80 or update proxy_pass accordingly |
There was a problem hiding this comment.
| # Ensure Vaultwarden is bound to 127.0.0.1:80 or update proxy_pass accordingly | |
| # Ensure Vaultwarden is bound to <your-server-ip>:80 or update proxy_pass accordingly |
| server_name your-domain.com; | ||
|
|
||
| location / { | ||
| proxy_pass http://127.0.0.1:80; |
There was a problem hiding this comment.
| proxy_pass http://127.0.0.1:80; | |
| proxy_pass http://<your-server-ip>:80; |
| ``` | ||
|
|
||
| Replace `your_generated_token_here` with the secure admin token you created. | ||
|
|
There was a problem hiding this comment.
I did notice one important note about the method used for generating admin token.
I get a message that reads:
rajie@vaultwarden:~/vaultwarden$ sudo docker logs vaultwarden
/--------------------------------------------------------------------\
| Starting Vaultwarden |
| Version 1.35.4 |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the |
| official channels to report bugs/features, regardless of client. |
| Send usage/configuration questions or feature requests to: |
| https://github.com/dani-garcia/vaultwarden/discussions or |
| https://vaultwarden.discourse.group/ |
| Report suspected bugs/issues in the software itself at: |
| https://github.com/dani-garcia/vaultwarden/issues/new |
\--------------------------------------------------------------------/
[NOTICE] You are using a plain text `ADMIN_TOKEN` which is insecure.
Please generate a secure Argon2 PHC string by using `vaultwarden hash` or `argon2`.
See: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page#secure-the-admin_token
However, it is not a blocker and i guess users can generate a more secure token if they want later.


Updated using Vaultwarden on Ubuntu 24.04 to replace existing documentation for using Vaultwarden Password Manager. All components update to latest version and switched from using a brittle version of Caddy to using NGINX for reverse proxy.